Fixes #5954

LGTM. Let's backport this to 3.4 and cut a v3.4.3.

✅ #5968

Does anything special need to be done to merge these? How does History.markdown work with parallel branches?

@pathawks Thank you! In the future, you may use script/backport-pr to backport these changes. The steps I follow are:

1. Merge this PR with @jekyllbot like normal. All your work on master is now done.
2. Checkout the backport branch in Backport #5957 to 3.4.x #5968 and run all tests locally via script/cibuild. If tests pass, then merge the PR.
3. Checkout the 3.4-stable branch. From here you will make the release. Do not commit any of the following manually, simply stage your changes.
4. Pull the changes to ensure you have the merged code, and run script/cibuild again, just to be absolutely sure.
5. Add an item to the History.markdown for this version & the backport PR (the syntax should be quite clear from previous releases), and bump the version in lib/jekyll/version.rb.
6. Run bundle exec rake site:generate to generate the necessary files in docs/.
7. Stage all changes to the History, the version file, and the docs folder but do not commit them.
8. Run bundle exec rake release.
9. Use git log to get the SHA-1 hash for the last commit with all your non-code changes. Checkout the master branch again, and cherry-pick that commit from the 3.4-stable branch. Make sure to re-align the histories and resolve conflicts as needed. Push this change to master (it should just update the History.markdown, the version.rb file, and some files in docs/). Once this has been properly committed, you may need to run bundle exec rake site:generate in order to get the files right, but it should work without this (famous last words!).
10. Write a release post. If you run bundle exec rake site:releases:new[3.4.3] a properly-organized post will be created. I've had a bit of fun with the last 2 patch release posts, so feel free to write what you wish. It needn't be too long.
11. Propose the release post in another PR and ping me. & the documentation affinity team.

Then you're done. 🎉 If you don't mind, I would love for you to do this release. You have been granted permission to publish the jekyll gem on RubyGems.org. I'll be back online tomorrow, March 21, if you have any questions. Feel free to email me or ping me in the Jekyll Slack. Thank you! ✨

The steps I follow are:

😮 Whoa! looks like a lot of hassle to release a patch-update with backports. (More prone to human-errors). I was under the impression that this would've been automated with a shell script and JekyllBot.

@parkr I'm on it. We should add these directions to https://jekyllrb.com/docs/maintaining/

@jekyllbot: merge +bug

@parkr I'm not authorized to push to master (protected branch), so you may have to be the one to cherry-pick 610d46134688c33ebc73fdaa5bfbffe0a65d42ca to master

Edit: I can just include it in my release post PR 👍